| Managing Runtime Data | Accessing the Runtime Hierarchy Data | |
Most applications require user-entered input Data and inference-generated output data to be "packaged" (into a String Variable or a Text File) for sharing, storage and retrieval at runtime. There are two sets of commands to enable this:
·@EncodeData used with @DecodeData
·@HierarchyToStr/@HierarchyToFile used with @HierarchyFromStr/@HierarchyFromFile
Both sets of commands generate/interpret the packaged data in either TXT or XML formats.
The @EncodeData Command can be used to automatically package all the data captured using Dialogs for the runtime session. This command can also be used to package any other specified object data. The @DecodeData command is used to "unpackage" the data into their Objects variables.
The @HierarchyToStr (and @HierarchyToFile) commands is used for packaging the generated Hierarchy output for the runtime session.
String variables are limited to 64K in size except when the string is defined as variable length and also is assigned its value via the @EncodeData and/or the @HierarchyToStr commands in this situation the string has an unlimited size. It is important to note the restriction on the use of unlimited length string variables; these strings can only be assigned values longer than 64K chars via the @EncodeData and/or the @HierarchyToStr commands, in other words they cannot be assigned, copied or manipulated in any other way.
The main purpose of this is to allow XML data, which is often massive in size, to be sent and received from Knowledge Builder rich client Web applications using strings rather than files.